Article 4 direction area

There is a problem

78 issue of type invalid category value

Bellingham Local Centre

reference: Bel1
name: Bellingham Local Centre
article-4-direction
permitted-development-rights: undefined
Class e
uprns
address-texts
geometry: MULTIPOLYGON (((-0.021592 51.432254,-0.019956 51.432674,-0.020002 51.432756,-0.020068 51.432768,-0.020073 51.432775,-0.020156 51.432754,-0.020129 51.432712,-0.020198 51.432689,-0.020221 51.432731,-0.020266 51.432721,-0.020315 51.432797,-0.020392 51.432778,-0.020379 51.432751,-0.020420 51.432741,-0.020453 51.432792,-0.020492 51.432784,-0.020425 51.432676,-0.020465 51.432665,-0.020441 51.432625,-0.020479 51.432616,-0.020508 51.432659,-0.020584 51.432641,-0.020601 51.432667,-0.020679 51.432648,-0.020664 51.432623,-0.020697 51.432614,-0.020688 51.432599,-0.020729 51.432586,-0.020755 51.432624,-0.020866 51.432594,-0.020854 51.432573,-0.020876 51.432567,-0.020865 51.432550,-0.020883 51.432544,-0.020902 51.432574,-0.020944 51.432563,-0.020971 51.432602,-0.021013 51.432593,-0.021036 51.432631,-0.021070 51.432621,-0.021050 51.432584,-0.021058 51.432582,-0.021036 51.432546,-0.021149 51.432516,-0.021211 51.432626,-0.021245 51.432618,-0.021215 51.432565,-0.021332 51.432538,-0.021346 51.432558,-0.021335 51.432562,-0.021343 51.432576,-0.021511 51.432539,-0.021414 51.432390,-0.021463 51.432377,-0.021497 51.432435,-0.021550 51.432422,-0.021562 51.432444,-0.021590 51.432437,-0.021585 51.432430,-0.021638 51.432416,-0.021613 51.432382,-0.021664 51.432368,-0.021592 51.432254)),((-0.017515 51.434083,-0.017363 51.433419,-0.017328 51.433328,-0.017314 51.433323,-0.017108 51.433366,-0.017129 51.433411,-0.017135 51.433410,-0.017155 51.433444,-0.017233 51.433429,-0.017239 51.433459,-0.017162 51.433474,-0.017165 51.433488,-0.017146 51.433491,-0.017137 51.433475,-0.017119 51.433479,-0.017122 51.433497,-0.017099 51.433501,-0.017102 51.433519,-0.017168 51.433506,-0.017173 51.433537,-0.017258 51.433521,-0.017264 51.433550,-0.017184 51.433568,-0.017199 51.433647,-0.017132 51.433661,-0.017142 51.433699,-0.017189 51.433691,-0.017192 51.433698,-0.017154 51.433707,-0.017166 51.433731,-0.017302 51.433710,-0.017306 51.433737,-0.017228 51.433764,-0.017265 51.433949,-0.017278 51.433947,-0.017284 51.433962,-0.017195 51.433982,-0.017205 51.434038,-0.017283 51.434021,-0.017306 51.434128,-0.017515 51.434083)),((-0.017279 51.433182,-0.017142 51.432901,-0.016896 51.432452,-0.016604 51.432517,-0.016636 51.432567,-0.016718 51.432549,-0.016737 51.432583,-0.016821 51.432564,-0.016839 51.432597,-0.016756 51.432614,-0.016793 51.432682,-0.016876 51.432666,-0.016896 51.432699,-0.016811 51.432716,-0.016850 51.432782,-0.016932 51.432765,-0.016951 51.432800,-0.016868 51.432818,-0.016885 51.432851,-0.016960 51.432985,-0.017044 51.432968,-0.017049 51.432983,-0.016807 51.433034,-0.016853 51.433124,-0.017004 51.433095,-0.017023 51.433128,-0.017105 51.433113,-0.017122 51.433134,-0.016996 51.433164,-0.017003 51.433179,-0.017044 51.433173,-0.017048 51.433186,-0.016963 51.433204,-0.016970 51.433222,-0.016949 51.433227,-0.016963 51.433255,-0.017279 51.433182)),((-0.018664 51.432987,-0.018234 51.433092,-0.018308 51.433209,-0.018378 51.433191,-0.018395 51.433209,-0.018582 51.433152,-0.018537 51.433078,-0.018553 51.433074,-0.018593 51.433143,-0.018723 51.433109,-0.018711 51.433068,-0.018724 51.433066,-0.018722 51.433034,-0.018700 51.433037,-0.018664 51.432987)))
point: POINT (-0.018752 51.432967)
notes
entry-date: 2026-02-25
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve London Borough of Lewisham’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL